Automatic provisioning of Wi-Fi connections for trailers

ABSTRACT

In one embodiment, a device of a tractor unit determines that the tractor unit is connected to a trailer via physical cabling. The device sends, via the physical cabling, a powerline communication (PLC) message to the trailer that includes a service set identifier (SSID) and password for a Wi-Fi transceiver of the tractor unit. The Wi-Fi transceiver of the tractor unit receives an association request sent wirelessly from a Wi-Fi transceiver of the trailer that is based on the sent SSID and password. The device establishes the Wi-Fi transceiver of trailer as a Wi-Fi client of the Wi-Fi transceiver of the tractor unit.

TECHNICAL FIELD

The present disclosure relates generally to computer networks, and, moreparticularly, to the automatic provisioning of Wi-Fi connections fortrailers.

BACKGROUND

In general, the Internet of Things (IoT) refers to the next evolution ofcomputer networking in which many devices that are not traditionallynetworked are now connected to the Internet, for purposes of remotemonitoring, remote control, and enhanced functionality. One example ofthis expansion of networking capabilities can be found in the shippingand trucking industry, whereby shipping trucks are increasingly beingoutfitted to communicate via the Internet.

In a typical configuration, the cabin of a tractor unit may include aWi-Fi access point that communicates with a Wi-Fi client on the trailer,as well as an external interface, such as a cellular connection, thatallows the tractor unit to send and receive data via the Internet. Eachtime a trailer is loaded onto a tractor unit, the connection between thetwo Wi-Fi networks needs to be established. While a seemingly simpleoperation, the nature of the trucking industry presents certain hurdlesto ensure that the wireless connection between tractor unit and traileris established correctly. First, there are typically several entitiesinvolved in any given transport of a load (e.g., the trailer may beowned by one entity, the payload in the trailer owned by another, andthe tractor unit owned by a third entity). Second, the Wi-Fi pairingsbetween trailers and tractor units is also relatively short lived innature, as the trailer is often disconnected from the tractor unit upondelivery. Third, there are often many tractor units and trailers locatedat a given warehouse or other location, greatly increasing the potentialfor a tractor unit Wi-Fi to be paired with the wrong trailer Wi-Fi. Forthese and other reasons, pairing the networks of a trailer and a tractorunit remain challenging.

BRIEF DESCRIPTION OF THE DRAWINGS

The embodiments herein may be better understood by referring to thefollowing description in conjunction with the accompanying drawings inwhich like reference numerals indicate identically or functionallysimilar elements, of which:

FIGS. 1A-1B illustrate an example communication network;

FIG. 2 illustrates an example network device/node;

FIG. 3 illustrates an example transportation vehicle;

FIG. 4 illustrates an example architecture for automaticallyprovisioning a Wi-Fi connection for a trailer;

FIG. 5 illustrates an example of limiting the Wi-Fi pairing range anddirection for a trailer;

FIG. 6 illustrates an example simplified procedure for pairing the Wi-Fiof a tractor unit to a trailer; and

FIG. 7 illustrates an example simplified procedure for pairing the Wi-Fiof a trailer to a tractor unit.

DESCRIPTION OF EXAMPLE EMBODIMENTS Overview

According to one or more embodiments of the disclosure, a device of atractor unit determines that the tractor unit is connected to a trailervia physical cabling. The device sends, via the physical cabling, apowerline communication (PLC) message to the trailer that includes aservice set identifier (SSID) and password for a Wi-Fi transceiver ofthe tractor unit. The Wi-Fi transceiver of the tractor unit receives anassociation request sent wirelessly from a Wi-Fi transceiver of thetrailer that is based on the sent SSID and password. The deviceestablishes the Wi-Fi transceiver of trailer as a Wi-Fi client of theWi-Fi transceiver of the tractor unit.

In further embodiments, a device of a trailer receives, via physicalcabling connecting the trailer to a tractor unit, a powerlinecommunication (PLC) message that includes a service set identifier(SSID) and password for a Wi-Fi transceiver of the tractor unit. A Wi-Fitransceiver of the trailer sends an association request to the Wi-Fitransceiver of the tractor unit that is based on the received SSID andpassword. The Wi-Fi transceiver of the trailer establishes itself as aWi-Fi client of the Wi-Fi transceiver of the tractor unit. The Wi-Fitransceiver of the trailer sends a wireless communication to the Wi-Fitransceiver of the tractor unit. In turn, the tractor unit transmits thecommunication via the Internet to a destination.

DESCRIPTION

A computer network is a geographically distributed collection of nodesinterconnected by communication links and segments for transporting databetween end nodes, such as personal computers and workstations, or otherdevices, such as sensors, etc. Many types of networks are available,ranging from local area networks (LANs) to wide area networks (WANs).LANs typically connect the nodes over dedicated private communicationslinks located in the same general physical location, such as a buildingor campus. WANs, on the other hand, typically connect geographicallydispersed nodes over long-distance communications links, such as commoncarrier telephone lines, optical lightpaths, synchronous opticalnetworks (SONET), synchronous digital hierarchy (SDH) links, orPowerline Communications (PLC), and others. Other types of networks,such as field area networks (FANs), neighborhood area networks (NANs),personal area networks (PANs), etc. may also make up the components ofany given computer network.

In various embodiments, computer networks may include an Internet ofThings network. Loosely, the term “Internet of Things” or “IoT” (or“Internet of Everything” or “IoE”) refers to uniquely identifiableobjects (things) and their virtual representations in a network-basedarchitecture. In particular, the IoT involves the ability to connectmore than just computers and communications devices, but rather theability to connect “objects” in general, such as lights, appliances,vehicles, heating, ventilating, and air-conditioning (HVAC), windows andwindow shades and blinds, doors, locks, etc. The “Internet of Things”thus generally refers to the interconnection of objects (e.g., smartobjects), such as sensors and actuators, over a computer network (e.g.,via IP), which may be the public Internet or a private network.

Often, IoT networks operate within a shared-media mesh networks, such aswireless or PLC networks, etc., and are often on what is referred to asLow-Power and Lossy Networks (LLNs), which are a class of network inwhich both the routers and their interconnect are constrained. That is,LLN devices/routers typically operate with constraints, e.g., processingpower, memory, and/or energy (battery), and their interconnects arecharacterized by, illustratively, high loss rates, low data rates,and/or instability. IoT networks are comprised of anything from a fewdozen to thousands or even millions of devices, and supportpoint-to-point traffic (between devices inside the network),point-to-multipoint traffic (from a central control point such as a rootnode to a subset of devices inside the network), and multipoint-to-pointtraffic (from devices inside the network towards a central controlpoint).

Fog computing is a distributed approach of cloud implementation thatacts as an intermediate layer from local networks (e.g., IoT networks)to the cloud (e.g., centralized and/or shared resources, as will beunderstood by those skilled in the art). That is, generally, fogcomputing entails using devices at the network edge to provideapplication services, including computation, networking, and storage, tothe local nodes in the network, in contrast to cloud-based approachesthat rely on remote data centers/cloud environments for the services. Tothis end, a fog node is a functional node that is deployed close to fogendpoints to provide computing, storage, and networking resources andservices. Multiple fog nodes organized or configured together form a fogsystem, to implement a particular solution. Fog nodes and fog systemscan have the same or complementary capabilities, in variousimplementations. That is, each individual fog node does not have toimplement the entire spectrum of capabilities. Instead, the fogcapabilities may be distributed across multiple fog nodes and systems,which may collaborate to help each other to provide the desiredservices. In other words, a fog system can include any number ofvirtualized services and/or data stores that are spread across thedistributed fog nodes. This may include a master-slave configuration,publish-subscribe configuration, or peer-to-peer configuration.

FIG. 1A is a schematic block diagram of an example simplifiedcommunication network 100 illustratively comprising nodes/devices atvarious levels of the network, interconnected by various methods ofcommunication. For instance, the links may be wired links or sharedmedia (e.g., wireless links, PLC links, etc.) where certain nodes, suchas, e.g., routers, sensors, computers, etc., may be in communicationwith other devices, e.g., based on connectivity, distance, signalstrength, current operational status, location, etc.

Specifically, as shown in the example network 100, three illustrativelayers are shown, namely the cloud 110, fog 120, and IoT device 130.Illustratively, the cloud 110 may comprise general connectivity via theInternet 112, and may contain one or more datacenters 114 with one ormore centralized servers 116 or other devices, as will be appreciated bythose skilled in the art. Within the fog layer 120, various fognodes/devices 122 may execute various fog computing resources on networkedge devices, as opposed to datacenter/cloud-based servers or on theendpoint nodes 132 themselves of the IoT layer 130. Data packets (e.g.,traffic and/or messages sent between the devices/nodes) may be exchangedamong the nodes/devices of the computer network 100 using predefinednetwork communication protocols such as certain known wired protocols,wireless protocols, PLC protocols, or other shared-media protocols whereappropriate. In this context, a protocol consists of a set of rulesdefining how the nodes interact with each other.

Those skilled in the art will understand that any number of nodes,devices, links, etc. may be used in the computer network, and that theview shown herein is for simplicity. Also, those skilled in the art willfurther understand that while the network is shown in a certainorientation, the network 100 is merely an example illustration that isnot meant to limit the disclosure.

FIG. 1B illustrates an example vehicle communication system 140,according to various embodiments. In particular, vehicle communicationsystem 140 may include any or all of the following components: a vehicle160, a roadside unit (RSU) 150, and/or a remote supervisory service 170.Generally, vehicle 160 may be any form of vehicle configured to movefrom one physical location to another such as, but not limited to, cars,buses, trucks, boats, trains, aerial vehicles, and the like. In manycases, vehicle 160 may be configured to transport people and/or cargo.Further, vehicle 160 may be an autonomous vehicle, semi-autonomousvehicle, or manually-operated vehicle, according to the variousembodiments herein.

In some embodiments, vehicle communication system 140 may be a specificimplementation of communication network 100. Notably, supervisoryservice 170 may be implemented at the cloud layer 110, such as at aparticular server 116 in a data center 114 or, alternatively, acrossmultiple servers 116, such as part of a cloud-based service. Similarly,RSU 150 may be a fog node 122 at fog computing layer 120, while vehicle160 may be viewed as an IoT node 132 at IoT layer 130. Thus, vehicle 160may communicate directly with RSU 150, and/or via other IoT nodes 132(e.g., other vehicles, etc.), and RSU 150 may provide some degree ofprocessing over the communicated data.

RSU 150 may communicate with supervisory service 170 via a WAN, such asthe Internet 112 or another WAN. For example, RSU 150 may communicatewith supervisory service 170 by leveraging a hardwired networkconnection, cellular or other wireless connection, satellite connection,or the like. Communications between vehicle 160 and RSU 150 maygenerally be wireless and use any form of known wireless communication(e.g., Wi-Fi, cellular, light-based, etc.).

As would be appreciated, vehicle 160 may comprise its own local network,to allow the various components of vehicle 160 to communicate with oneanother. For example, vehicle 160 may comprise any number ofsub-networks, such as a Controller Area Network (CAN) bus, an IPnetwork, etc., to allow the various systems of vehicle 160 tocommunicate with one another. Such system may include, but are notlimited to, an engine control unit (ECU), a battery management system(BMS) that manages the local battery of vehicle 160, an advanced driverassistance system (ADAS) system, and the like. A local gateway ofvehicle 160 may provide communicative connectivity between the localnetwork of vehicle 160 and other devices. For example, the local gatewayof vehicle 160 may provide wireless connectivity to RCU 150 locatedalong road 166 on which vehicle 160 is traveling. In some embodiments,vehicle 160 may also communicate directly with supervisory service 170via the Internet 112 or another WAN, such as by leveraging a wirelessconnection to a cellular or satellite-based network.

FIG. 2 is a schematic block diagram of an example computing device/node200 that may be used with one or more embodiments described herein e.g.,as any of the devices shown in FIGS. 1A-1B above or any of the devicesdescribed further below. The device may comprise one or more networkinterfaces 210 (e.g., wired, wireless, cellular, PLC, etc.), at leastone processor 220, and a memory 240 interconnected by a system bus 250,as well as a power supply 260 (e.g., battery, plug-in, etc.).

The network interface(s) 210 contain the mechanical, electrical, andsignaling circuitry for communicating data over links coupled to thenetwork 100. The network interfaces may be configured to transmit and/orreceive data using a variety of different communication protocols. Note,further, that the nodes may have two or more different types of networkconnections 210, e.g., wireless and wired/physical connections, and thatthe view herein is merely for illustration. Also, while the networkinterface 210 is shown separately from power supply 260, for fog modulesusing PLC, the network interface 210 may communicate through the powersupply 260, or may be an integral component of the power supply. In somespecific configurations the PLC signal may be coupled to the power linefeeding into the power supply.

The memory 240 comprises a plurality of storage locations that areaddressable by the processor 220 and the network interfaces 210 forstoring software programs and data structures associated with theembodiments described herein. The processor 220 may comprise hardwareelements or hardware logic adapted to execute the software programs andmanipulate the data structures 245. An operating system 242, portions ofwhich are typically resident in memory 240 and executed by theprocessor, functionally organizes the device by, among other things,invoking operations in support of software processes and/or servicesexecuting on the device. These software processes and/or services maycomprise an illustrative communication process 248, as described herein.

It will be apparent to those skilled in the art that other processor andmemory types, including various computer-readable media, may be used tostore and execute program instructions pertaining to the techniquesdescribed herein. Also, while the description illustrates variousprocesses, it is expressly contemplated that various processes may beembodied as modules configured to operate in accordance with thetechniques herein (e.g., according to the functionality of a similarprocess). Further, while the processes have been shown separately, thoseskilled in the art will appreciate that processes may be routines ormodules within other processes.

As noted above, the shipping/trucking industry is deploying more andmore IoT applications. Many of these applications use a Wi-Fi client ona trailer that is connected to the Wi-Fi access point on the maintractor cabin for data logging and accessing external connection overbroadband links, such as a cellular connection. Every time a trailer isconnected to a tractor unit, the connection between the two Wi-Finetworks needs to be established. This seemingly simple operation hasmajor logistics issues facing the industry today including, but notlimited to, the following:

-   -   There are several parties involved in this transaction most of        whom have a short-term association with the other parties. For        example, the trailer may be owned by one entity, the payload        owned by another, and the tractor unit itself owned by a third        entity. In addition, the driver may or may not be an actual        employee of the truck owner and may be working on a contract        basis for certain durations or trips. All this implies sharing        credentials required for pairing of the Wi-Fi is neither        logistically possible nor desirable.    -   The Wi-Fi pairings between trailers and tractor units is        relatively short-lived in nature. Typically, the truck driver        picks up the load (e.g., the loaded trailer) and drives it to        the destination. Once there, the trailer is typically        disconnected from the tractor unit and the tractor unit is        attached to another trailer for the next trip. Unlike a typical        wireless device which may have a handful of stored service set        identifiers (SSIDs) that it encounters on a frequent basis, the        trailer may never get paired with the same tractor unit ever        again. This greatly increases the chances that user intervention        will be needed to complete the Wi-Fi pairing.    -   At the docks, warehouses, and other locations where tractor        units and trailers are mated, there are often multiple tractor        units and trailers within close proximity of one another. This        often makes it difficult to identify and associate the correct        Wi-Fi networks.    -   Truck drivers may not be technically adept in configuring Wi-Fi        networks.    -   Typically, trailers are not equipped with user interfaces like        keyboards & screens to configure the clients with the proper        selection of SSIDs and user credentials, such as passwords.    -   Given the transient nature of the relationship between truck        drivers and trucking companies, trucking companies may not want        to share their network details, such as SSIDs and passwords,        with drivers. Furthermore, frequently changing the SSIDs and        passwords could also increase security, but present a logistical        nightmare for the people on the ground, as well.

Automatic Provisioning of Wi-Fi Connections for Trailers

The techniques herein introduce an approach to pairing the Wi-Finetworks of IoT enabled trailers and tractor units in an automatedmanner. In some aspects, Wi-Fi provisioning can be achieved byleveraging an existing hardwired connection between a trailer and atractor unit. Indeed, trailers and tractor units today are typicallyconnected using physical cabling, such as a J560 or other cable. Thetechniques herein propose leveraging these existing cables for purposesof establishing a wireless connection between the two. For example,Wi-Fi provisioning data can be exchanged between a trailer and a tractorunit via Powerline Communications (PLC) messaging over an existing J560cable that connects the trailer to the tractor unit.

Specifically, according to one or more embodiments of the disclosure asdescribed in detail below, a device of a tractor unit determines thatthe tractor unit is connected to a trailer via physical cabling. Thedevice sends, via the physical cabling, a powerline communication (PLC)message to the trailer that includes a service set identifier (SSID) andpassword for a Wi-Fi transceiver of the tractor unit. The Wi-Fitransceiver of the tractor unit receives an association request sentwirelessly from a Wi-Fi transceiver of the trailer that is based on thesent SSID and password. The device establishes the Wi-Fi transceiver oftrailer as a Wi-Fi client of the Wi-Fi transceiver of the tractor unit.All of this can be achieved with no user intervention.

Illustratively, the techniques described herein may be performed byhardware, software, and/or firmware, such as in accordance with thecommunication process 248, which may include computer executableinstructions executed by the processor 220 (or independent processor ofinterfaces 210) to perform functions relating to the techniquesdescribed herein.

Operationally, the techniques use an already existing cable and plugdesign that will be equipped with low speed, low throughput PLC andmechanisms for exchanging Wi-Fi credential and authenticationinformation, to link the Wi-Fi of a trailer to that of a tractor unit.Doing so allows the tractor unit to relay data between the trailer andthe Internet via a cellular or other external connection, effectivelyacting as a hotspot for the trailer.

FIG. 3 illustrates vehicle 160 in greater detail, according to variousembodiments. As shown, vehicle 160 may comprise a tractor unit 302 and atrailer 304. During use, trailer 304 may be loaded with cargo fordelivery and physically coupled with trailer 304, thereby allowingtractor unit 302 to tow trailer 304 to its destination.

In all cases, physical cabling 306 is also connected between tractorunit 302 and trailer 304 for purposes of controlling the variousmechanisms of trailer 304 from tractor unit 302. For example, physicalcabling 306 may be used to convey control signals from tractor unit 302to the turn signals, tail lamps, and license plate lamps of trailer 304.This allows the driver of tractor unit 302 to control the variouslighting functions of trailer 304 directly from the cabin of tractorunit 302.

As would be appreciated, there are a number of different standards forthe physical cabling between tractor units and trailers. In general,these typically fall within two common categories: 7-pin and 13-pinconnectors. However, other standards provide for 5 pin and 15 pinconnectors, for commercial trucks. Non-commercial trucks may use otherstandards that utilize 4, 5, or 6 pin connectors. A non-exhaustivelisting of standards that can be used in conjunction with the techniquesherein is as follows:

-   -   International Standards Organization (ISO) standard 11446 for        13-pin connectors.    -   ISO standard 7638-2 for 7-pin connectors.    -   ISO standard 1724 for 7-pin, Type 12N connectors.    -   ISO standard 3732 for 7-pin, Type 12S connectors.    -   ISO standard 1724 for 5-pin connectors.    -   ISO standard 12098 for 15-pin connectors.    -   ISO standard 7638-1 for 7-pin trailer connectors.    -   ISO standard 1185 for 7-pin, Type 24N connectors.    -   ISO standard 3731 for 7-pin, Type 24S connectors.

Generally speaking, the differences between the various connectorstandards lies in the amount of voltage conveyed and the trailerfeatures that are controlled. For example, different cabling standardsmay convey 12V of electricity, which is the most common voltage,although other standards provide for the use of 6V or 24V. Similarly,while most cabling standards provide for the control over the turnsignals and tail lights of the trailer, other cabling standards alsoallow for the control over the anti-lock braking (ABS) mechanism, rearfog lamps, brake wear indicators, etc. of the trailer.

In North America, the most common form of cabling between a trailer andtractor unit follows the Society of Automotive Engineers (SAE) J560standard. Physically, J560 connectors follow the ISO 1185 standard, butJ560 requires the use of 12V and higher currents than the 24V called forin the ISO standard. More specifically, the J560 standard specifies thefollowing line/pin configuration:

TABLE 1 Pin Signal Color 1 Ground White 2 Lamps - clearance, markerBlack lamps, identification lamps 3 Left Turn Signal Yellow 4 Stop LampsRed 5 Right Turn Signal Green 6 Tail Lamps, License Plate Brown Lamps 7ABS brakes, Auxiliary Blue Equipment

FIG. 4 illustrates an example architecture 400 for automaticallyprovisioning a Wi-Fi connection for a trailer, according to variousembodiments. For purpose of illustrating the techniques herein, cabling306 is shown with seven pins/wires, such as in accordance with the J560standard. However, as would be appreciated, the techniques herein arenot limited as such and can be used with any of the various standardsfor wiring a trailer to a tractor unit.

As noted above, trailer 304 and tractor unit 302 may each be equippedwith a Wi-Fi transceiver such as Wi-Fi transceivers 406 and 408,respectively. More specifically, Wi-Fi transceiver 406 of trailer 304may attach itself as a client to Wi-Fi transceiver 408 of tractor 302,which functions as a Wi-Fi access point. Also located on tractor unit302 may be an external interface 410 communicatively coupled to Wi-Fitransceiver 408 to allow tractor unit 302 to communicate externally. Forexample, external interface 410 may comprise a cellular or satellitetransceiver. Thus, Wi-Fi transceiver 408 of tractor unit 302 may relaycommunications between Wi-Fi transceiver 406 of trailer 304 and theInternet. For example, Wi-Fi transceiver 406 may send sensor data fromsensors located on trailer 304 to an Internet-based monitoring service(e.g., temperature readings from a refrigerated trailer, etc.).

According to various embodiments, trailer 304 and tractor unit 302 mayalso be equipped with its own PLC module (PLM), such as PLM 402 and PLM404, respectively. As shown, PLMs 402 and 404 may be coupled to aplurality of the wires of cabling 306, such as the ground wire, andwires 2-3 shown. More specifically, the transmit (Tx) port of PLM 402may be coupled with the receive (Rx) port of PLM 404 via wire 2 and thereceive port of PLM 402 may be coupled with the transmit port of PLM 404via wire 3, and both of PLMs 402, 404 coupled to the ground wire ofcabling 306. Of course, other wires of cabling 306 could be used tocouple PLM 402 and PLM 404, as desired.

As would be appreciated, Wi-Fi transceiver 406 and PLM 402 may beimplemented as a single unit or as separate units in communication withone another. Similarly, Wi-Fi transceiver 408 and PLM 404 may beimplemented as a single unit or as separate units in communication withone another. In the separate unit case, both the PLM and Wi-Fitransceiver may be viewed as a single device/apparatus, for purposes ofthe teachings herein.

To connect Wi-Fi transceiver 406 of trailer 304 as a client of Wi-Fitransceiver 408 of tractor unit 302, architecture 400 may operate asfollows:

-   -   1. When cabling 306 is connected and tractor unit 302 started,        Wi-Fi transceiver 408 may send SSID and password information to        PLM 404.    -   2. PLM 404 transmits the SSID and password information to PLM        402 via cabling 306.    -   3. On trailer 304, PLM 402 receives the SSID and password        information for Wi-Fi transceiver 408 and passes this        information on to Wi-Fi transceiver 406.    -   4. Wi-Fi transceiver 406 uses the provided SSID and password        information to send an association request to Wi-Fi transceiver        408, to wirelessly establish itself as a client of Wi-Fi        transceiver 408.    -   5. In some embodiments, as an additional security measure, Wi-Fi        transceiver 406 may send its ID information, such as the MAC        address of Wi-Fi transceiver 406, back to Wi-Fi transceiver 408        via PLMs 402-404. In turn, Wi-Fi transceiver 408 can use the        provided ID to prevent other devices (e.g., spoofing devices)        from joining the Wi-Fi network of tractor unit 302.

Once Wi-Fi transceiver 406 is connected wirelessly with Wi-Fitransceiver 408, Wi-Fi transceiver 406 can then leverage the highbandwidth connection of external interface 410 to pass data to and fromthe Internet.

Of note is that the above mechanisms also increase security overexisting pairing approaches, as Wi-Fi transceiver 408 of tractor unit302 can opt to block any other Wi-Fi transceivers as clients whose MACaddresses do not match that of Wi-Fi transceiver 406 transmitted in step5 above.

Wi-Fi transceiver 408 may disconnect Wi-Fi transceiver 406 as a clientunder any or all of the following scenarios:

-   -   Tractor unit 302 is turned off.    -   Cabling 306 is disconnected.    -   A request to decouple Wi-Fi transceivers 406-408 is received        (e.g., via the Internet, via a user interface, etc.).

As would be appreciated, the above procedures can also be repeated, tore-establish Wi-Fi transceiver 406 as a client of Wi-Fi transceiver 408.For example, if Wi-Fi transceiver 406 was disconnected as a result ofthe driver of tractor unit 302 shutting off the truck and turning thetruck back on, this may automatically initiate re-establishment of thepairing, on detection of cabling 306 still being connected.

In some cases, once Wi-Fi transceiver 406 is established as a client ofWi-Fi transceiver 408, PLC communications between PLMs 402 and 404 maybe disabled. In doing so, the communication over cabling 306 only occurswhen the truck is turned on and all the systems are initialized (e.g.,the engine of tractor unit 302 starts, power is supplied to trailer 304to start its lights, etc.) and turns off quickly after initialization.This can be performed on the order of seconds, meaning that the PLCcommunications will not pose a safety concern by interruptingfunctioning of the lights and other components of trailer 304 whiledriving.

Detection of the connection of cabling 306 between tractor unit 302 andtrailer 304 can be achieved in a number of ways. In some embodiments, aconnector of cabling 306 may be configured with a mechanical or magneticswitch that is activated when plugged into its corresponding connector.In such cases, the state of the switch can be used to determine thatcabling 306 is coupled to both tractor unit 302 and to trailer 304. Infurther embodiments, the connectors of cabling 306 can be outfitted withnear field communication (NFC) hardware that detects the coupling oftractor unit 302 and trailer 304 via cabling 306. In furtherembodiments, PLMs 402-404 may also regularly exchange keepalive packets,to detect the presence of a physical connection via cabling 306.

In some embodiments, whenever a new connection via cabling 306 isdetected and Wi-Fi transceiver 406 provides its ID information back totractor unit 302, tractor unit 302 may use external interface 410 toreport this ID to an Internet-based service. Such reporting may alsoinclude GPS location and/or timestamp information that can be used bythe service for any or all of the following:

-   -   For an initial connection, the service can verify that tractor        unit 302 is at a known GPS location (e.g., a warehouse or pickup        point), to ensure the pairing happened at a valid location.    -   To perform analytics or other recordkeeping, the service can        also record the initial pairing between tractor unit 302 and        trailer 304. Such information is valuable to answer whether the        truck driver picked up the load on schedule.    -   If the GPS location is not an expected location of pairing, the        service can generate an alert. For example, if the switch is not        at an expected location, this can indicate a potential robbery        or breakdown.    -   In cases where the ID of trailer 304 does not match the expected        ID, the service can also generate an alert to the truck driver,        as this may indicate that the driver picked up the wrong load.        This can greatly reduce costly and time-consuming mistakes.

FIG. 5 illustrates an example of limiting the Wi-Fi pairing range anddirection for a trailer. Assume, for example, that tractor unit 302 andtrailer 304 are equipped with multi-antenna Wi-Fi transceivers, whichcan be used to communicate with other access points in the yard and forother purposes. In such cases, in various embodiments, thesetransceivers can be used to restrict the wireless pairing/provisioningbetween tractor unit 302 and trailer 304 to a specific range and/ordirection. For example, a rogue device operating near a truck rest area,dock, warehouse, etc., may attempt to connect with either of trailer 304or tractor unit 302.

In further cases, a malicious entity may attempt to connect with trailer304 or tractor unit 302 while driving alongside vehicle 160. Forexample, as shown, if tractor unit 302 and trailer 304 are connected viaphysical cabling 306, their corresponding Wi-Fi transceivers may onlyconnect with one another within a valid pairing region 502. Thus, ifanother entity, such as vehicle 504 attempts to connect with the Wi-Fiof either trailer 304 or tractor unit 302, the connection attempt may beblocked based on vehicle 504 being located outside of valid pairingregion 502 (e.g., based on the estimated direction and distance tovehicle 504).

Said differently, the range (e.g., based on signal strength) anddirection associated with a received association request can be used tofurther ensure that trailer 304 only associates with the Wi-Fi oftractor unit 302 and vice-versa. For tractor unit 302, this means thatthe pairing direction would be directly behind it and for trailer 304,the pairing direction will be directly in front of it. Thus, if thereceived signal is from any other direction, the attempted connectionmay be blocked. In some cases, tractor unit 302 may report the blockedconnection to the supervisory service. FIG. 6 illustrates an examplesimplified procedure for pairing the Wi-Fi of a tractor unit to atrailer in a network in accordance with one or more embodimentsdescribed herein. For example, a non-generic, specifically configureddevice (e.g., device 200), such as a device of a tractor unit, mayperform procedure 600 by executing stored instructions (e.g., process248). The procedure 600 may start at step 605, and continues to step610, where, as described in greater detail above, the device maydetermine that the tractor unit is connected to a trailer via physicalcabling. For example, the cabling may be J560 cabling or other ISOstandard cabling. In various embodiments, the device may determine thatthe tractor unit is connected to the trailer based on a signal from amagnetic or mechanical switch mounted to the cabling, NFC circuitryassociated with the cabling, or even via detection of a PLC signal onthe cabling.

At step 615, as detailed above, the device may send, via the physicalcabling, a PLC message to the trailer that includes a service setidentifier (SSID) and password for a Wi-Fi transceiver of the tractorunit. Such a transceiver may be integrated directly into the device or,alternatively, be in communication therewith.

At step 620, the Wi-Fi transceiver of the tractor unit receives anassociation request sent wirelessly from a Wi-Fi transceiver of thetrailer that is based on the sent SSID and password, as described ingreater detail above. In addition, in some cases, the trailer may alsosend an identifier, such as a MAC address, for its Wi-Fi transceiverthat can be used to prevent other Wi-Fi transceiver from associatingwith the transceiver of the tractor unit as clients. Such an identifiercan also be sent by the tractor unit to an Internet-based service toverify that the correct trailer was attached to the tractor unit (e.g.,by matching a location, timestamp, and trailer ID to expected values).

At step 625, as detailed above, the device may establish the Wi-Fitransceiver of trailer as a Wi-Fi client of the Wi-Fi transceiver of thetractor unit. Once paired, the Wi-Fi transceiver of the trailer may senda communication to the Wi-Fi transceiver of the tractor unit and, inturn, forward the communication on to the Internet via an externalinterface of the tractor unit, such as a cellular or satellitetransceiver. Procedure 600 then ends at step 630.

FIG. 7 illustrates an example simplified procedure for pairing the Wi-Fiof a trailer to a tractor unit, according to various embodiments. Forexample, a non-generic, specifically configured device (e.g., device200), such as a device of a trailer, may perform procedure 700 byexecuting stored instructions (e.g., process 248). The procedure 700 maystart at step 705, and continues to step 710, where, as described ingreater detail above, the device may receive, via physical cablingconnecting the trailer to a tractor unit, a PLC message that includes anSSID and password for a Wi-Fi transceiver of the tractor unit.

At step 715, as detailed above, a Wi-Fi transceiver of the trailer maysend an association request to the Wi-Fi transceiver of the tractor unitthat is based on the received SSID and password. Such a transceiver ofthe trailer may be integrated directly into the device or be incommunication therewith. In some embodiments, the device may also sendan identifier for the Wi-Fi transceiver of the trailer to the tractorunit (e.g., a MAC address or other identifier). This can be used, forexample, for purposes of ensuring that the tractor unit is coupled tothe right trailer and the like.

At step 720, the Wi-Fi transceiver of trailer is established as a Wi-Ficlient of the Wi-Fi transceiver of the tractor unit, as described ingreater detail above. In other words, the Wi-Fi transceiver of thetractor unit may operate as an access point for the Wi-Fi transceiver ofthe trailer.

At step 725, as detailed above, a wireless communication may be sentfrom the Wi-Fi transceiver of the trailer to the Wi-Fi transceiver ofthe tractor unit. In some embodiments, the tractor unit may transmit thecommunication via the Internet to a destination. For example, thecommunication may include sensor data from the trailer that is reportedto an Internet-based monitoring service. Conversely, the Wi-Fitransceiver of the tractor unit may also forward a communication fromthe Internet to the Wi-Fi transceiver of the trailer, such as a query,control command, etc. Procedure 700 then ends at step 730.

It should be noted that while certain steps within procedures 600-700may be optional as described above, the steps shown in FIGS. 6-7 aremerely examples for illustration, and certain other steps may beincluded or excluded as desired. Further, while a particular order ofthe steps is shown, this ordering is merely illustrative, and anysuitable arrangement of the steps may be utilized without departing fromthe scope of the embodiments herein. Moreover, while procedures 600-700are described separately, certain steps from each procedure may beincorporated into each other procedure, and the procedures are not meantto be mutually exclusive.

The techniques described herein, therefore, allow for the Wi-Fi pairingof a trailer to a tractor unit without requiring any additionalintervention by a user. In some aspects, the techniques herein alsoprovide additional security measures over existing approaches, byensuring that the correct trailer is connected to the correct tractorunit.

While there have been shown and described illustrative embodiments thatprovide for the automatic provisioning of Wi-Fi for trailers, it is tobe understood that various other adaptations and modifications may bemade within the spirit and scope of the embodiments herein. For example,while certain embodiments are described herein with respect toprovisioning a trailer to the Wi-Fi of a tractor unit, the techniquesherein are not limited as such and can be used for other forms oftransportation vehicles, as well. In addition, while certain protocolsare shown, such as Wi-Fi, other suitable protocols may be used,accordingly.

The foregoing description has been directed to specific embodiments. Itwill be apparent, however, that other variations and modifications maybe made to the described embodiments, with the attainment of some or allof their advantages. For instance, it is expressly contemplated that thecomponents and/or elements described herein can be implemented assoftware being stored on a tangible (non-transitory) computer-readablemedium (e.g., disks/CDs/RAM/EEPROM/etc.) having program instructionsexecuting on a computer, hardware, firmware, or a combination thereof.Accordingly, this description is to be taken only by way of example andnot to otherwise limit the scope of the embodiments herein. Therefore,it is the object of the appended claims to cover all such variations andmodifications as come within the true spirit and scope of theembodiments herein.

What is claimed is:
 1. A method, comprising: determining, by a device ofa tractor unit, that the tractor unit is connected to a trailer viaphysical cabling, wherein the physical cabling forms a connectionbetween a powerline communication (PLC) module of the tractor unit and aPLC module of the trailer, wherein the PLC modules enable PLCcommunications between the tractor unit and trailer over the physicalcabling; sending, by the device and via the PLC communications, a PLCmessage to the trailer that includes a service set identifier (SSID) andpassword for a Wi-Fi transceiver of the tractor unit; receiving, at theWi-Fi transceiver of the tractor unit, an association request sentwirelessly from a Wi-Fi transceiver of the trailer that is based on thesent SSID and password; establishing, by the device, the Wi-Fitransceiver of the trailer as a Wi-Fi client of the Wi-Fi transceiver ofthe tractor unit; receiving, at the device of the tractor unit, a PLCmessage from the trailer that includes an identifier for the Wi-Fitransceiver of the trailer; verifying, at the device of the tractor unitand using the received identifier, that the trailer is correctlyestablished to the tractor unit based on an external Internet-basedservice; and using, by the device, the received identifier to preventspoofed Wi-Fi transceivers from joining the Wi-Fi transceiver of thetractor unit as clients.
 2. The method as in claim 1, furthercomprising: receiving, at the Wi-Fi transceiver of the tractor unit, acommunication from the Wi-Fi transceiver of the trailer; andtransmitting the received communication via the Internet to adestination.
 3. The method as in claim 2, wherein the receivedcommunication is transmitted via a cellular transceiver of the tractorunit.
 4. The method as in claim 1, wherein the physical cabling is J560cabling.
 5. The method as in claim 1, wherein the identifier for theWi-Fi transceiver of the trailer comprises a media access control (MAC)address.
 6. The method as in claim 1, further comprising: sending anindication of the received identifier, a timestamp, and locationinformation to an Internet-based service.
 7. The method as in claim 1,wherein the PLC message is sent to the trailer in response to thetractor unit starting.
 8. The method as in claim 1, wherein determiningthat the tractor unit is connected to the trailer via the physicalcabling comprises: receiving a signal from a switch mounted to thecabling.
 9. A method, comprising: receiving, at a device of a trailerand via powerline communication (PLC) communications enabled by aconnection formed between a PLC module of the trailer and a PLC moduleof a tractor unit over physical cabling connecting the trailer and thetractor unit, a PLC message that includes a service set identifier(SSID) and password for a Wi-Fi transceiver of the tractor unit;sending, by a Wi-Fi transceiver of the trailer, an association requestto the Wi-Fi transceiver of the tractor unit that is based on thereceived SSID and password; establishing the Wi-Fi transceiver of thetrailer as a Wi-Fi client of the Wi-Fi transceiver of the tractor unit;sending a wireless communication from the Wi-Fi transceiver of thetrailer to the Wi-Fi transceiver of the tractor unit, wherein thetractor unit transmits the communication via the Internet to adestination; and sending a PLC message from the trailer that includes anidentifier for the Wi-Fi transceiver of the trailer, wherein the Wi-Fitransceiver of the tractor unit verifies, using the sent identifier,that the trailer is correctly established to the tractor unit based onan external Internet-based service and prevents spoofed Wi-Fitransceivers from joining the Wi-Fi transceiver of the tractor unit asclients.
 10. The method as in claim 9, wherein the physical cabling isJ560 cabling.
 11. The method as in claim 9, wherein the identifier forthe Wi-Fi transceiver of the trailer comprises a media access control(MAC) address.
 12. An apparatus, comprising: a powerline communication(PLC) network interface; a Wi-Fi transceiver; a processor coupled to thePLC network interface and the Wi-Fi transceiver that is configured toexecute one or more processes; and a memory configured to store aprocess executable by the processor, the process when executedconfigured to: determine that a tractor unit is connected to a trailervia physical cabling, wherein the physical cabling forms a connectionbetween the PLC network interface of the tractor unit and a PLC moduleof the trailer, wherein the PLC network interface and the PLC moduleenable PLC communications between the tractor unit and the trailer overthe physical cabling; send, via the physical cabling and the PLC networkinterface, a PLC message to the trailer that includes a service setidentifier (SSID) and password for the Wi-Fi transceiver of theapparatus; receive, at the Wi-Fi transceiver of the apparatus, anassociation request sent wirelessly from a Wi-Fi transceiver of thetrailer that is based on the sent SSID and password; establish, by theapparatus, the Wi-Fi transceiver of the trailer as a Wi-Fi client of theWi-Fi transceiver of the apparatus; receive, by the apparatus, a PLCmessage from the trailer that includes an identifier for the Wi-Fitransceiver of the trailer; verify, using the received identifier, thatthe trailer is correctly established to the tractor unit based on anexternal Internet-based service; and use the received identifier toprevent spoofed Wi-Fi transceivers from joining the Wi-Fi transceiver ofthe tractor unit as clients.
 13. The apparatus as in claim 12, whereinthe process when executed is further configured to: receive, at theWi-Fi transceiver of the apparatus, a communication from the Wi-Fitransceiver of the trailer; and transmit the received communication viathe Internet to a destination.
 14. The apparatus as in claim 13, whereinthe received communication is transmitted via a cellular transceiver ofthe tractor unit.
 15. The apparatus as in claim 12, wherein theapparatus determines that the tractor unit is connected to the trailervia physical cabling by exchanging PLC-based keepalive packets with thetrailer.
 16. The apparatus as in claim 12, wherein the process whenexecuted is further configured to: block an association request based ona range or direction associated with the blocked association requestrelative to the Wi-Fi transceiver.
 17. The apparatus as in claim 12,wherein the apparatus determines that the tractor unit is connected tothe trailer via the physical cabling by: receiving a signal from aswitch mounted to the cabling.